v7.5.1

Compare Source

Patch Changes

• Fix prerendering when a loader returns a redirect (#​13365)
• Updated dependencies:
  • react-router@7.5.1
  • @react-router/node@7.5.1
  • @react-router/serve@7.5.1

v7.5.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.5.1

v7.5.1

Compare Source

Patch Changes

• Updated dependencies:
  • react-router@7.5.1
  • @react-router/node@7.5.1
  • @react-router/express@7.5.1

v14.3.1

Compare Source

Changelog: https://docs.cypress.io/app/references/changelog#14-3-1

v15.3.1

Compare Source

v4.3.4

Compare Source

Patch Changes

• #​442 57611d9 Thanks @​JounQin! - fix: add more extension aliases for ts source/declaration files

• #​444 bd45fcd Thanks @​JounQin! - fix(deps): bump unrs-resolver which resolves #​406, #​409, #​437

v4.3.3

Compare Source

Patch Changes

• #​433 834b11e Thanks @​JounQin! - chore: bump unrs-resolver to v1.6.0

v0.4.20

Compare Source

• Don't warn on nested HOC calls (fixes #​79)
• Fix false positive with as const (fixes #​80)

v15.3.1

Compare Source

v7.5.1

Compare Source

Patch Changes

• Fix single fetch bug where no revalidation request would be made when navigating upwards to a reused parent route (#​13253)

• When using the object-based route.lazy API, the HydrateFallback and hydrateFallbackElement properties are now skipped when lazy loading routes after hydration. (#​13376)

  If you move the code for these properties into a separate file, you can use this optimization to avoid downloading unused hydration code. For example:

  createBrowserRouter([
    {
      path: "/show/:showId",
      lazy: {
        loader: async () => (await import("./show.loader.js")).loader,
        Component: async () => (await import("./show.component.js")).Component,
        HydrateFallback: async () =>
          (await import("./show.hydrate-fallback.js")).HydrateFallback,
      },
    },
  ]);

• Properly revalidate prerendered paths when param values change (#​13380)

• UNSTABLE: Add a new unstable_runClientMiddleware argument to dataStrategy to enable middleware execution in custom dataStrategy implementations (#​13395)

• UNSTABLE: Add better error messaging when getLoadContext is not updated to return a Map" (#​13242)

• Do not automatically add null to staticHandler.query() context.loaderData if routes do not have loaders (#​13223)

  • This was a Remix v2 implementation detail inadvertently left in for React Router v7
  • Now that we allow returning undefined from loaders, our prior check of loaderData[routeId] !== undefined was no longer sufficient and was changed to a routeId in loaderData check - these null values can cause issues for this new check
  • ⚠️ This could be a "breaking bug fix" for you if you are doing manual SSR with createStaticHandler()/<StaticRouterProvider>, and using context.loaderData to control <RouterProvider> hydration behavior on the client

• Fix prerendering when a loader returns a redirect (#​13365)

• UNSTABLE: Update context type for LoaderFunctionArgs/ActionFunctionArgs when middleware is enabled (#​13381)

• Add support for the new unstable_shouldCallHandler/unstable_shouldRevalidateArgs APIs in dataStrategy (#​13253)